| // base path
This is currently set to "resources/", and if your pages are all in a single folder,
then you don't need to change this. However if your site spans
multiple folders in a complex heirarchy you will need
to have a centralised location for all the component scripts and images. You can specify the
path to the main scripts on a per-page basis with the script tags, eg:
<script language="javascript" src="../../resources/sniffer.js"></script>
But the scripts themselves need an absolute path, so baseHREF is used
to define this. I recommend you design and customise the layout from a single template that's in the
parent directory of the resources folder (like in the zip file),
and then change the baseHREF when you're ready to go live. Either of two methods can be used,
an absolute path, eg:
var baseHREF = "http://www.domain.com/mysite/resources/";
or a path relative to the base directory, eg:
var baseHREF = "/mysite/resources/";
The first method is slightly slower, but will work when you view the pages locally, although
it will still be drawing its scripts and images from your live directory. The second method
is more efficient but will break locally ... unless your local file system
happens to mirror that of your web server (highly unlikely). However it breaks in
a really nice way - no errors are generated, you simply don't see a navbar.
An alternative, if you want to be able to surf your site locally exactly as
live, is to use an absolute local path when you build or edit your site, and then
change it to an absolute url when you publish. eg:
var baseHREF = "C:/Cake/Internet/WebPages/dropdown/resources/";
for testing, could become
var baseHREF = "/dropdown/resources/";
when it goes live
Note that even though local addresses in Windows are split with a backslash \
(or a colon : in MacOS) you will need
to change these to forward slashes / for the benefit of the script.
This will only function in Internet Explorer, because other browsers use different
syntax for local addresses.
However, and this is very groovy, you could add a self-referencing function, which checks the document url to discover
if you're looking at a local or live copy, and then adjusts baseHREF to suit. This stress-reducing
idea comes courtesy of Alan Lam - paste this whole code fragment into your custom.js,
replacing the current baseHREF definition, and then changing the paths to suit your situation:
var baseHREF = "/dropdown/resources/";
var thisLoc = document.location.href;
if ((thisLoc.indexOf("http://")==-1)&&(thisLoc.indexOf("wysiwyg://")==-1)) {
baseHREF = "C:/Cake/Internet/WebPages/dropdown/resources/";
if (op5||op6) { baseHREF = "file://localhost/C:/Cake/Internet/WebPages/dropdown/resources/"; }
if (ns4||ns6||mz7) { baseHREF = "file:///C|/Cake/Internet/WebPages/dropdown/resources/"; }
}
|
